HBAnyware 3.0a15 Linux Installation Instructions

This installation kit contains the following components:

      HBAnyware version 3.0a15
      SSC version 3.0a15
      DFC Library version 80.162-7
      Lputil version 2.0a14
      HBAAPI version 2.1.c
      DFC helper module

Dependencies:

	lpfc driver version 8.1.6.6 or later
					 
HBAnyware requires that the lpfc driver module be installed.

HBAnyware requires a minimum screen resolution of 1024 x 768.

HBAnyware requires the kernel development environment as described here:

This kit installs the Emulex Application Helper Module for the
currently running kernel.  Since this installation procedure builds
the module for the currently running kernel, the kernel development
environment must be installed.  For systems running Red Hat Enterprise
Linux (RHEL) 4, the appropriate kernel-devel package is required; for
example, a system with the 2.6.9-22.EL kernel would need the
kernel-devel-2.6.9-22.EL package, and a system with the 2.6.9-22.ELsmp
kernel would need the kernel-smp-devel-2.6.9-22.EL package.  For
systems running SuSE Linux Enterprise Server (SLES) 9, the appropriate
kernel-source package is required; for example, a system with the
2.6.5-7.139-bigsmp kernel would need the kernel-source-2.6.5-7.139
package.


A log of each installation and uninstallation is recorded in the
following file:

   /usr/src/lpfcdfc/utils-install.log


Installing HBAnyware:

 1. Copy the applications kit tar file to a directory on the install machine
 2. cd to the directory which you copied the tar file
 3. Untar the file: tar -xvf tarfilename 
 4. cd (change directory) to the "ElxLinuxApps.." directory created by step 3
 5. su to root
 6. If earlier HBAnyware version currently installed, type : ./uninstall
 7. Run the install script: ./install
 8. When prompted, answer the following question:

    Select desired mode of operation for HBAnyware

    1   Local Mode     : HBA's on this Platform can be managed by HBAnyware clients on this platform only.
    2   Managed Mode   : HBA's on this Platform can be managed by local or remote HBAnyware clients
    3   Remote Mode    : Same as '2' plus HBAnyware clients on this Platform can manage local and remote clients.

	Enter the number '1' or '2' or '3'


 9. When prompted, answer the following question:
    
	Do you want to allow user to make subsequent management mode changes using 'set_operating_mode' script
    Enter the letter 'Y' for yes or 'N' for no

10. Installation Complete: type /usr/sbin/hbanyware/hbanyware       
    to start GUI 
	                    or type /usr/sbin/hbanyware/hbacmd list 
    to run script utility


Uninstalling HBAnyware

 1. Complete steps 1 through 5 from "Installing HBAnyware" above.
 2. Run the uninstall script: ./uninstall


Running the HBAnyware GUI

 1. su to root
 2. Run the script /usr/sbin/hbanyware/hbanyware 



HBAnyware Help:
To view the HBAnyware help pages or to access the Emulex Technical support pages you must have one of the 
following web browsers installed: mozilla, konqueror

PLEASE NOTE:
Some Web browsers attempt to continually reload the HBAnyware online help rendering
it unusable. In this case, disable the Web browser's JavaScript capability. Refer
to the Web browser's documentation for instructions.



Helpful scripts

/usr/sbin/hbanyware/stop_hbanyware - This script will stop all HBAnyware daemons and GUIs. 
                                     Run this script before attempting to unload the lpfc driver.

/usr/sbin/hbanyware/start_elxhbamgr - This script will re-start the management server daemon. 
                                     Run this if you manually load the lpfc driver.

/usr/sbin/hbanyware/set_operating_mode - This script will re-issue the HBAnyware management mode
                                     configuration question described in installation step 8 above.


KNOWN ISSUES:

*HBAnyware, Driver Params, RHEL & SLES, mkinitrd & modprobe issue*

    HBAnyware's Driver Params support for Unix (all varieties) was originally designed to write each lpfc
    driver param to a separate line in the config file.

    The file used is as follows:
      For Linux, driver versions post-8.x: /etc/modprobe.conf

    HBAnyware releases through and including 3.0 use this design.

    We have found that for certain recent releases of Linux, if the lpfc driver params are written to the
    config file in this fashion, problems appear with mkinitrd and modprobe, such that only the last driver
    param is used by the program.

    Here is a summary:

    mkinitrd
      RHEL 4 - problem
      SLES 9 - OK

    modprobe
      RHEL 4 - OK
      SLES 10 - problem

    To work around the problem, do the following steps:

    1. Use HBAnyware to modify the driver params as desired.
    2. Manually edit the modprobe.conf file, and concatenate all of the driver params into a single line,
       separating each driver param with a space character. For example:
       options lpfc lpfc_max_luns=100 lpfc_log_verbose=0x1
